Skip to main content

Entities & Enums

Entity​

Entities are the building blocks of your data model.
Each entity represents a specific type of data and defines its structure through a set of fields (columns).
Well-designed entities are the foundation for clean relationships, efficient querying and robust business logic.

Entity configuration view

Entities consist of different column types, each tailored to a specific kind of data and input behavior:

  • ID
    Reserved for unique identifiers. Ensures each record in an entity is distinct.

  • String
    Text-based input, suitable for names, descriptions, codes, and mixed alphanumeric values.

  • Numeric types
    Byte, Int16, Int32, Int64, UInt16, UInt32, UInt64, Decimal, Double
    Used for numeric values with different ranges and precision.
    A specialized number picker restricts entries to valid numeric input.

  • Boolean
    Simple true/false values, edited via a checkbox.

  • Date & Time
    Date and time pickers for temporal values.
    These fields are nullable: a separate checkbox allows explicitly setting the value to null.
    When null is selected, the picker is hidden to indicate that no value is set.

  • Link
    URL or hyperlink fields. Also nullable, so you can explicitly indicate “no link”.

  • Enum
    A dropdown selection from a predefined list of values.
    Nullable, so “no selection” can be distinguished from a concrete value.

  • Computed
    Values derived from other data (e.g. calculations or transformations).
    Computed fields are also nullable, which is useful when an expression cannot or should not resolve to a value.

For nullable types such as Date, Time, Link, Enum, and Computed, the UI always provides an explicit null option.
Selecting this option hides the usual input control and clearly communicates that the field is intentionally left without a value.

Enum​

An Enum (enumeration) defines a fixed set of named values.
Enums are ideal for representing states, categories or other closed value sets (e.g. Status: Open / InProgress / Closed).

Using Enums in your entities:

  • improves data integrity (only allowed values can be stored),
  • simplifies UI input (dropdown instead of free text),
  • makes your data model easier to understand.
Enum configuration view
info

The Enum section in the UI is not fully implemented yet and currently serves as a visual preview.
There is no final functionality behind it at this point.